So, you would rather change all the links which currently don't specify a version (that's the majority of them right now), and have them specify whatever version is appropriate.

I can do that, although then we'd still be prone to accidentally linking the wrong version -- as some of these links did, note some going to /v0.5.2/, some to /v0.6.1/, etc.

We could use the mdBook preproc to interpolate in the RGBDS version number, so that there's a single source of truth for it? (Perhaps {{#include "rgbds_ver.txt"}} inline would work, but if not, we can always add our own plumbing.)

@ISSOtm

We could use the mdBook preproc to interpolate in the RGBDS version number, so that there's a single source of truth for it? (Perhaps {{#include "rgbds_ver.txt"}} inline would work, but if not, we can always add our own plumbing.)

This may be a cool 'further improvement', albeit it entails a lot of additional work + new config, templating etc so I wouldn't say it's a priority right now. Feel free to open a Issue detailing the idea.

@Rangi42

So, you would rather change all the links which currently don't specify a version (that's the majority of them right now), and have them specify whatever version is appropriate.

I can do that, although then we'd still be prone to accidentally linking the wrong version -- as some of these links did, note some going to /v0.5.2/, some to /v0.6.1/, etc.

We don't have an "alias" / link to the "latest" minor of 1.x on the rgbds website, right?

This may be a cool 'further improvement', albeit it entails a lot of additional work

If we can make it work with just the built-in {{#include}}, then that's hardly any additional work. I should give that a try, and open an issue to track the item if more work is involved. Let's say tomorrow after a good night of sleep 😅 (pushed back due to the debate in #151 eating all of my motivation)